Release notes

2026r3

Reduced unnecessary recreation when using MAM API

Previously, when updating a media asset with markers or media segments using the MAM API, such as the POST /completeMediaAssets call, these markers and media segments were always deleted and recreated, even when unchanged. This could generate unnecessary change log entries and impact performance. This issue has been fixed in this version. If there are no changes to these concepts, they are not recreated.

Prevent moving components using MAM API

Previously, it was possible to move a video, audio, or subtitling component from one media asset to another via the MAM API, while this is not allowed in the Mediagenix Base platform itself. This issue has been fixed. Attempting to reassign a component to a different media asset returns a 422 error, with message code MAM-00044: The media asset on component [ID] does not match the media asset itself.